Method and system for enabling communication between blockchains on heterogeneous blockchain networks

ABSTRACT

A system for enabling communication between blockchains on heterogeneous blockchain networks. The system can include a sending blockchain network comprised of a sending blockchain that includes a plurality of blocks, each block including a block header and one or more transaction values associated with an identification request transmitted by the sending blockchain. The system can include a directory service node configured to receive the identification request from the sending blockchain, and identify a receiving blockchain, which forms part of a receiving blockchain network. The system can include an identity service node configured to receive a trust request from the directory service node to determine whether a valid trust certificate is available for the receiving blockchain and enable communication between the sending blockchain and the receiving blockchain, when the valid trust certificate is determined to be available.

FIELD

The present disclosure relates to enabling communication betweenblockchains on heterogeneous blockchain networks.

BACKGROUND

The number of blockchains, such as banks or other financial institutionsoperating on blockchain networks has grown at a rapid pace in the lastdecade. However, these blockchain networks remain isolated, operating intheir own respective silos. Many heterogeneous blockchain networks areunable to communicate with each other, such as because of the use ofdifferent communication protocols, formatting standards, etc.

In some cases, if a blockchain network attempts to retrieve informationfrom an external (outside the blockchain) source, each node in theblockchain network would have to perform the operation. But in suchcases, because each node acts individually and an external source (e.g.,a heterogeneous blockchain network) is used, there is no guarantee thateach node will receive the same answer from the external source. Thislack of homogeneity can break the consensus and therefore render theblockchain invalid.

The present disclosure provides technical solutions to theaforementioned technical problems of blockchain interoperability.

SUMMARY

The present disclosure provides a description of exemplary systems andmethods to allow blockchains (e.g., blockchain based banks) on multipleheterogeneous blockchain networks to discover each other and establish atrusted connection to enable communication (e.g., payment flows) betweenthe blockchains. Once a communication channel between the blockchains isestablished, it allows the blockchains to communicate with each otherand perform an end-to-end payment flow despite their different messagingformats.

The system can include a sending blockchain network comprised of asending blockchain that includes a plurality of blocks, each blockincluding a block header and one or more transaction values associatedwith an identification request transmitted by the sending blockchain.The system can include a directory service node configured to receivethe identification request from the sending blockchain, and identify areceiving blockchain which forms part of a receiving blockchain network.The system can include an identity service node configured to receive atrust request from the directory service node to determine whether avalid trust certificate is available for the receiving blockchain, andenable communication between the sending blockchain and the receivingblockchain, when the valid trust certificate is determined to beavailable.

The method can include transmitting an identification request from asending blockchain to a directory service node, wherein the sendingblockchain includes a plurality of blocks, each block including a blockheader and one or more transaction values associated with theidentification request, and the sending blockchain forms a part of asending blockchain network. The method can include identifying, via thedirectory service node, a receiving blockchain that forms part of areceiving blockchain network. The method can include receiving, at anidentity service node, a trust request from the directory service nodeto determine whether a valid trust certificate is available for thereceiving blockchain. The method can include enabling communicationbetween the sending blockchain and the receiving blockchain, when thevalid trust certificate is determined to be available.

BRIEF DESCRIPTION OF THE DRAWING FIGURES

The scope of the present disclosure is best understood from thefollowing detailed description of exemplary embodiments when read inconjunction with the accompanying drawings. Included in the drawings arethe following figures:

FIG. 1 illustrates a system for enabling communication betweenblockchains on heterogeneous blockchain networks in accordance withexemplary embodiments.

FIG. 2 illustrates a method for enabling communication betweenblockchains on heterogeneous blockchain networks in accordance withexemplary embodiments.

FIG. 3 illustrates a system for communication between blockchains onheterogeneous blockchain networks in accordance with exemplaryembodiments.

FIG. 4 illustrates a method for communication between blockchains onheterogeneous blockchain networks in accordance with exemplaryembodiments.

FIG. 5 is a block diagram illustrating computer system architecture inaccordance with exemplary embodiments.

Further areas of applicability of the present disclosure will becomeapparent from the detailed description provided hereinafter. It shouldbe understood that the detailed description of exemplary embodiments areintended for illustration purposes only and are, therefore, not intendedto necessarily limit the scope of the disclosure.

DETAILED DESCRIPTION Glossary of Terms

Blockchain—A public ledger of all transactions of a blockchain-basedcurrency or other data storage that may, in some case, not be related tofinancial transactions or other data transactions. One or more computingdevices may comprise a blockchain network, which may be configured toprocess and record transactions as part of a block in the blockchain.Once a block is completed, the block is added to the blockchain and thetransaction record thereby updated. In many instances, the blockchainmay be a ledger of transactions in chronological order, or may bepresented in any other order that may be suitable for use by theblockchain network. In some configurations, transactions recorded in theblockchain may include a destination address and a currency amount, suchthat the blockchain records how much currency is attributable to aspecific address. In some instances, the transactions are financial andothers not financial, or might include additional or differentinformation, such as a source address, timestamp, etc. In someembodiments, a blockchain may also or alternatively include nearly anytype of data as a form of transaction that is or needs to be placed in adistributed database that maintains a continuously growing list of datarecords hardened against tampering and revision, even by its operators,and may be confirmed and validated by the blockchain network throughproof of work and/or any other suitable verification techniquesassociated therewith. In some cases, data regarding a given transactionmay further include additional data that is not directly part of thetransaction appended to transaction data. In some instances, theinclusion of such data in a blockchain may constitute a transaction. Insuch instances, a blockchain may not be directly associated with aspecific digital, virtual, fiat, or other type of currency.

System and Method for Enabling Communication Between Blockchains onHeterogeneous Blockchain Networks

FIG. 1 illustrates an exemplary system 100 for enabling communicationbetween blockchains on heterogeneous blockchain networks. Heterogeneousblockchain networks, as used herein, can be any two or more blockchainnetworks with different layers, which may differ in the implementationof the networking, consensus, and application parts of the blockchain.Additionally, each of the heterogeneous blockchain networks can havetheir own validators that decide on the next block to commit to theblockchain.

In an exemplary embodiment, the system 100 can include a sendingblockchain network 110 (e.g., blockchain network A) comprised of atleast one sending blockchain (e.g., 120), and at least one node that maybe a computing system configured to perform functions related to theprocessing and management of the blockchain, including the generation ofblockchain data values, verification of proposed blockchaintransactions, verification of digital signatures, generation of newblocks, validation of new blocks, and maintenance of a copy of theblockchain.

A blockchain, as used herein, can include various types of entities suchas banks, financial institutions, or other nodes that at least partiallyoperate on a blockchain. The blockchain may be a distributed ledger thatis comprised of at least a plurality of blocks. Each block may includeat least a block header and one or more data values. Each block headermay include at least a timestamp, a block reference value, and a datareference value. The timestamp may be a time at which the block headerwas generated and may be represented using any suitable method (e.g.,UNIX timestamp, DateTime, etc.).

The block reference value may be a value that references an earlierblock (e.g., based on timestamp) in the blockchain. In some embodiments,a block reference value in a block header may be a reference to theblock header of the most recently added block prior to the respectiveblock.

In an exemplary embodiment, the block reference value may be a hashvalue generated via the hashing of the block header of the most recentlyadded block. The data reference value may similarly be a reference tothe one or more data values stored in the block that includes the blockheader. In an exemplary embodiment, the data reference value may be ahash value generated via the hashing of the one or more data values. Forinstance, the block reference value may be the root of a Merkle treegenerated using the one or more data values.

The use of the block reference value and data reference value in eachblock header may result in the blockchain being immutable. Any attemptedmodification to a data value would require the generation of a new datareference value for that block, which would thereby require thesubsequent block's block reference value to be newly generated, furtherrequiring the generation of a new block reference value in everysubsequent block. This would have to be performed and updated in everysingle node in the blockchain network prior to the generation andaddition of a new block to the blockchain in order for the change to bemade permanent. Computational and communication limitations may makesuch a modification exceedingly difficult, if not impossible, thusrendering the blockchain immutable.

In an exemplary embodiment, each block can include a block header andone or more transaction values associated with an identification request105 transmitted by a sending blockchain 120, such that the sendingblockchain 120 (e.g., Blockchain A) forms a part of the sendingblockchain network 110.

In an exemplary embodiment, the identification request 105 can includeinformation of a receiving blockchain that has to be identified. Forexample, if it's a financial institution based blockchain, theidentification request 105 can include: zip code information, which canprovide geographical/location information of a receiving blockchain,including its zip code; pricing information, which can provideinformation regarding the costs/fee etc. charged by a receivingblockchain for various transactions; foreign exchange (fx) information,which can provide any exchange rate related information charged by areceiving blockchain; and Unique identifier information of the receivingblockchain, for example, International Bank Account Number (IBAN) for abank based blockchain.

If the blockchain is a cryptocurrency based blockchain, theidentification request 105 can include information regarding mining,transaction fees, exchange fees, initial coin offerings etc. If theblockchain is a smart contract based blockchain, the identificationrequest 105 can include information regarding enforcement, tracking,tampering, expiry date, etc.

The identification request 105 can also include prior communicationinformation between a sending blockchain and a receiving blockchain,which can include the type of communication, nature of thecommunication, frequency of the communication, and/or substance of thecommunication. The one or more transaction values of the identificationrequest 105 can include the aforementioned information.

In an exemplary embodiment, the system 100 can include a directoryservice node 130 configured to receive the identification request 105from the sending blockchain 120, and identify a receiving blockchain 140(e.g., Blockchain B), which forms part of a receiving blockchain network150.

In an exemplary embodiment, the directory service node 130 can beconfigured to identify the receiving blockchain 140 by applying one ormore machine learning algorithms on the identification request. Machinelearning, as used herein, can be one or more algorithms, or combinationsthereof, to effectively perform a specific task without using explicitinstructions, relying on patterns and inference instead. For example,one or more of the classification, learning, clustering, neuralnetworks, reinforcement learning, supervised learning algorithms, etc.

In an exemplary embodiment, a support vector machine (SVM) can be usedas a machine learning technique to identify the receiving blockchain 140based on the identification request 105. Various methods can be used fortraining and building the SVM. One such method is described in U.S. Pat.No. 6,327,581, which is incorporated in its entirety by reference. Theinputs applied to the SVM can include one or more aspects of theidentification request such as zip code, pricing, fx, unique identifierand/or prior communication information, as previously described.

In an exemplary embodiment, the SVM can use zip code information as oneof the inputs to classify receiving blockchains (e.g., 140) based ontheir location with respect to the sending blockchain 120. Similarly,the SVM can use pricing information, fx information to classifyreceiving blockchains based on their cost effectiveness for varioustransactions. These are just a few examples. OF course the SVM can alsouse other/all the inputs to classify receiving blockchains based ondifferent aspects. The directory service node 130 can then identify thereceiving blockchain 140 based on the classification.

For example, if the classification by SVM identifies a receivingblockchain within a limited range of zip code of the sending blockchain,then the directory service node 130 can identify that as the receivingblockchain 140. Similarly, if the classification by SVM identifiesmultiple receiving blockchains within a given distance of the sendingblockchain, then the directory service node 130 can identify themultiple receiving blockchains as potential receiving blockchains. Insuch a scenario, to select only one of the potential receivingblockchains, the directory service node 130 can apply SVM techniques (orother machine learning techniques) to the potential multiple receivingblockchains based on some other input (other than zip code information)to identify the receiving blockchain 140. For example, directory servicenode 130 can apply SVM techniques based on fx fee inputs to classify thepotential multiple blockchains to identify the receiving blockchain 140.Alternately, the directory service node 130 can identify the receivingblockchain 140 based on its unique identifier.

In an exemplary embodiment, an artificial neural network can be used toidentify the receiving blockchain 140 based on the identificationrequest 105. Various methods can be used for training and building theartificial neural network. One such method is described in the article“A Step by Step Backpropagation Example” by Matt Mazur, available athttps://mattmazur.com/2015/03/17/a-step-by-step-backpropagation-example/.This article is incorporated in its entirety by reference.

In this referenced article, the weights and biases assigned to variousinputs can be based on preferences of the sending blockchain 120. Forexample, if the sending blockchain 120 prefers a receiving blockchainwith which it has had prior communication, then a higher weight can beassigned to the prior communication information. As the trainingproceeds, weights and biases for each node of the neural network can beadjusted based on the backpropagation.

In an exemplary embodiment, an identity service node 160 configured toreceive a trust request 115 from the directory service node 130 todetermine whether a valid trust certificate is available for thereceiving blockchain 140 and enable communication 125 between thesending blockchain 120 and the receiving blockchain 140, when the validtrust certificate is determined to be available.

A trust certificate, as used herein, can provide an indication of thetrustworthiness of the receiving blockchain 140. Factors that affect thetrustworthiness can be multi-faceted including prior performance,reputation, network, security details, etc. A trust certificate for ablockchain can be valid at a given point of time if the blockchain isdetermined to trustworthy in a given context at that time. The trustcertificate can be revoked later in time.

In an exemplary embodiment, once communication 125 is enabled betweenthe sending blockchain 120 and the receiving blockchain 140, continuousdata exchange between the sending blockchain 120 and receivingblockchain 140 in their respective blockchain networks can occur withouta re-verification of the valid trust certificate. Alternately, are-verification can take place after a given period of time (e.g., everyalternate day etc.)

In various exemplary embodiments, the sending blockchain network 110 caninclude multiple blockchains (e.g., blockchains 120, 135 etc.). Thereceiving blockchain network 150 can include multiple blockchains (e.g.,blockchain 140, 145 etc.). The directory service node 130 can form apart of the sending blockchain network 110 or can be external (notshown) to the sending blockchain network 110. Similarly, the identityservice node 160 can form a part of the sending blockchain network 110or can be external (not shown) to the sending blockchain network 110.

In an exemplary embodiment, the receiving blockchain network 150 canalso include a directory service node 155 and an identity service node165, with similar functionalities as discussed with respect to 130 and160 respectively, of the sending blockchain network 110.

FIG. 2 illustrates an exemplary method 200, which can be executed in thesystem 100 for enabling communication between blockchains onheterogeneous blockchain networks. The method 200 can include a step 210of transmitting an identification request (e.g., 105) from a sendingblockchain (e.g., 120) to a directory service node (e.g., 130), aspreviously described with respect to the system 100. The sendingblockchain can form a part of a sending blockchain network (e.g., 110),the blockchain being comprised of a plurality of blocks, each blockincluding a block header and one or more transaction values associatedwith the identification request.

The method 200 can include a step 220 of identifying, via the directoryservice node, a receiving blockchain (e.g., 140) that forms part of areceiving blockchain network (e.g., 150), as previously described withrespect to the system 100. The method 200 can include a step 230 ofreceiving, at an identity service node (e.g., 160), a trust request fromthe directory service node to determine whether a valid trustcertificate is available for the receiving blockchain, as previouslydescribed with respect to the system 100.

The method 200 can include a step 240 of enabling communication (e.g.,125) between the sending blockchain and the receiving blockchain, whenthe valid trust certificate is determined to be available, as previouslydescribed with respect to system 100.

Exemplary aspects of the method 200 can be similar to the previouslydescribed system 100. After enabling the communication as described insystem 100 and method 200, the communication 125 can be performed asdescribed in the subsequent sections.

System and Method for Communicating Between Blockchains on HeterogeneousBlockchain Networks

FIG. 3 shows an exemplary system 300 for communicating betweenblockchains on heterogeneous blockchain networks. The system 300 caninclude a sending blockchain 310 configured to transmit a first message305 via a sending blockchain protocol, such that the sending blockchain310 is comprised of a plurality of blocks, each block including a blockheader and one or more transaction values associated with the firstmessage 305, and the sending blockchain 310 forms a part of a sendingblockchain network 320 (e.g., Blockchain A).

A protocol (e.g., the sending blockchain protocol), as used herein, canrelate to any rules, syntax, semantics and synchronization ofcommunication between components of a messaging system. Protocols may beimplemented by hardware, software, or a combination of both.

Protocols may specify rules governing the communication. For example,rules regarding data formats and address formats for data exchange,address mapping, routing, detection of transmission errors,acknowledgments, information loss, sequence control, and flow control,etc.

Protocols may include, but are not limited to, one or more of thefollowing: Transmission Control Protocol (TCP) and the User DatagramProtocol (UDP) based protocols, automation protocols (e.g., Ethernet),Bluetooth (e.g., BNEP), file transfer protocols, instant messagingprotocols (e.g., BitMessage), link aggregation protocols (e.g., Nortel),OSI protocols (e.g., 802.11 Wi-Fi), routing protocols (e.g., IPv4,IPv6), HTTP protocols based on data formats (e.g., JSON, XML, etc.).

In an exemplary embodiment, the system 300 can include a sending adapternode 330 (e.g., Adapter-A) configured to receive the first message 305(in the sending blockchain protocol) from the sending blockchain 310 andconvert the first message 305 from the sending blockchain protocol to anadapter protocol.

In an exemplary embodiment, the general architecture of an adapter node(e.g., 330) can include an internal master protocol communicating toexternal slave devices and the data collected being used to update theinternal database of the adapter. When the external master requests fordata, the internal slave can collect data from the database and send itto the external master. There can be different schemes for handling thespontaneous reporting of events and commands. There can be differentphysical medium for communication on protocol-X & Y, which includeRS-232, RS-485, Ethernet, etc.

The conversion from one protocol to another, as disclosed herein, can bevia known techniques. An exemplary technique for converting from oneprotocol to another protocol is described in U.S. Pat. No. 7,966,012,incorporated herein by reference. Similarly, other exemplary techniquescan be used for protocol conversion, as described in U.S. Pat. Nos.6,070,196 and 6,208,904, both of which are incorporated herein byreference.

In an exemplary embodiment, the system 300 can include a receivingadapter node 340 (e.g., adapter B) configured to receive the firstmessage 315 (in the adapter protocol) from the sending adapter node 330and convert the first message 315 from the adapter protocol to areceiving blockchain protocol. The system can also include a receivingblockchain 350 configured to receive the first message 325 (in thereceiving blockchain protocol) from the receiving adapter node 340, andvalidate the first message 325, such that the receiving blockchain 350forms a part of the receiving blockchain network 360.

Validation of a message (e.g., 325) can provide certain well-definedguarantees for fitness, accuracy, and consistency for any type data intoan application or automated system. Data validation rules can be definedand designed using any of various methodologies and can be deployed inany of various contexts. For example, U.S. Pat. Nos. 7,594,033,7,512,711, 6,732,175, 6,732,175, and 7,146,422 describe severalmethodologies for data validation, all of which are incorporated hereinby reference.

In an exemplary embodiment, the receiving blockchain 350 can beconfigured to transmit a second message 335 to the receiving adapternode 340 via the receiving blockchain protocol. The receiving adapternode 340 can be configured to convert the second message 335 from thereceiving blockchain protocol to the adapter protocol and transmit thesecond message 345 to the sending adapter node 330.

In an exemplary embodiment, the first message can be a payment requestfor a transaction between the sending blockchain 310 and the receivingblockchain 350. The second message can be a payment acceptedacknowledgment for a transaction between the sending blockchain 310 andthe receiving blockchain 350.

In an exemplary embodiment, the sending adapter node 330 can beconfigured to convert the second message 345 from the adapter protocolto a sending blockchain protocol. The sending adapter node 330 can befurther configured hash the second message 345 (in the sendingblockchain protocol) and store the hashed second message 355 in thesending blockchain network 320.

Hashing, as used herein, can include the use of any cryptographic hashdigest function, such as the Secure Hash Algorithm SHA-256. In exemplaryembodiments, the hashing algorithms used herein may be anycryptographically safe hashing algorithm.

In an exemplary embodiment, the receiving blockchain 350 can beconfigured to hash the validated first message 325 (in the receivingblockchain protocol) and store the hashed first message 365 in thereceiving blockchain network 360.

In an exemplary embodiment, the sending adapter node 330 can form a partof the sending blockchain network 320 or can be external (not shown) tothe sending blockchain network 320. Similarly, the receiving adapternode 340 can form a part of the receiving blockchain network 360 or canbe external (not shown) to the receiving blockchain network 360.

In an exemplary embodiment, the sending blockchain network 320 caninclude multiple blockchains (e.g., 310, 370). Similarly, the receivingblockchain network 360 can also include multiple blockchains (e.g., 350,380).

FIG. 4 illustrates an exemplary method 400, which can be executed in thesystem 300 for communication between blockchains on heterogeneousblockchain networks. The method 400 can include a step 410 oftransmitting a first message (e.g., 305) from a sending blockchain(e.g., 310) to a sending adapter node (e.g., 330) via a sendingblockchain protocol, as previously described with respect to the system300.

The sending blockchain can be comprised of a plurality of blocks, eachblock including a block header and one or more transaction valuesassociated with the first message, and the sending blockchain can form apart of a sending blockchain network (e.g., 110).

The method 400 can include a step 420 of converting the first message,via the sending adapter node, from the sending blockchain protocol to anadapter protocol. The method 400 can include a step 430 of transmittingthe first message from the sending adapter node to a receiving adapternode (e.g., 340), as previously described with respect to the system300.

The method 400 can include a step 440 of converting the first message,via the receiving adapter node, from the adapter protocol to a receivingblockchain protocol. The method 400 can include a step 450 oftransmitting the first message from the receiving adapter node to areceiving blockchain (e.g., 360), which can form a part of the receivingblockchain network, as previously described with respect to system 300.

The method 400 can include a step 460 of validating the first message atthe receiving blockchain, as previously described with respect to system300. Other exemplary aspects of the method 400 can be similar to thepreviously described system 300.

Various exemplary embodiments/aspects of the aforementioned system 100and 300, and method 200 and 400 can be implemented using a computersystem, using hardware, software, firmware, non-transitory computerreadable media having instructions stored thereon, or a combinationthereof and may be implemented in one or more computer systems or otherprocessing systems. Details of an exemplary computer system 500 aredescribed as follows.

Computer System Architecture

FIG. 5 illustrates the computer system 500 in which embodiments of thepresent disclosure, or portions thereof, may be implemented ascomputer-readable code. For example, the system 100 of FIG. 1 and thesystem 300 of FIG. 3 may be implemented in the computer system 500 usinghardware, software, firmware, non-transitory computer readable mediahaving instructions stored thereon, or a combination thereof and may beimplemented in one or more computer systems or other processing systems.Hardware, software, or any combination thereof may embody modules andcomponents used to implement the methods of FIGS. 2 and 4.

If programmable logic is used, such logic may execute on a commerciallyavailable processing platform configured by executable software code tobecome a specific purpose computer or a special purpose device (e.g.,programmable logic array, application-specific integrated circuit,etc.). A person having ordinary skill in the art may appreciate thatembodiments of the disclosed subject matter can be practiced withvarious computer system configurations, including multi-coremultiprocessor systems, minicomputers, mainframe computers, computerslinked or clustered with distributed functions, as well as pervasive orminiature computers that may be embedded into virtually any device. Forinstance, at least one processor device and a memory may be used toimplement the above described embodiments.

A processor unit or device as discussed herein may be a singleprocessor, a plurality of processors, or combinations thereof. Processordevices may have one or more processor “cores.” The terms “computerprogram medium,” “non-transitory computer readable medium,” and“computer usable medium” as discussed herein are used to generally referto tangible media such as a removable storage unit 518, a removablestorage unit 522, and a hard disk installed in hard disk drive 512.

Various embodiments of the present disclosure are described in terms ofthis exemplary computer system 500. After reading this description, itwill become apparent to a person skilled in the relevant art how toimplement the present disclosure using other computer systems and/orcomputer architectures. Although operations may be described as asequential process, some of the operations may in fact be performed inparallel, concurrently, and/or in a distributed environment, and withprogram code stored locally or remotely for access by single ormultiprocessor machines. In addition, in some embodiments the order ofoperations may be rearranged without departing from the spirit of thedisclosed subject matter.

Processor device 504 may be a special purpose or a general purposeprocessor device specifically configured to perform the functionsdiscussed herein. The processor device 504 may be connected to acommunications infrastructure 506, such as a bus, message queue,network, multi-core message-passing scheme, etc. The network may be anynetwork suitable for performing the functions as disclosed herein andmay include a local area network (LAN), a wide area network (WAN), awireless network (e.g., WiFi), a mobile communication network, asatellite network, the Internet, fiber optic, coaxial cable, infrared,radio frequency (RF), or any combination thereof. Other suitable networktypes and configurations will be apparent to persons having skill in therelevant art. The computer system 500 may also include a main memory 508(e.g., random access memory, read-only memory, etc.), and may alsoinclude a secondary memory 510. The secondary memory 510 may include thehard disk drive 512 and a removable storage drive 514, such as a floppydisk drive, a magnetic tape drive, an optical disk drive, a flashmemory, etc.

The removable storage drive 514 may read from and/or write to theremovable storage unit 518 in a well-known manner. The removable storageunit 518 may include a removable storage media that may be read by andwritten to by the removable storage drive 514. For example, if theremovable storage drive 514 is a floppy disk drive or universal serialbus port, the removable storage unit 518 may be a floppy disk orportable flash drive, respectively. In one embodiment, the removablestorage unit 518 may be non-transitory computer readable recordingmedia.

In some embodiments, the secondary memory 510 may include alternativemeans for allowing computer programs or other instructions to be loadedinto the computer system 500, for example, the removable storage unit522 and an interface 520. Examples of such means may include a programcartridge and cartridge interface (e.g., as found in video gamesystems), a removable memory chip (e.g., EEPROM, PROM, etc.) andassociated socket, and other removable storage units 522 and interfaces520 as will be apparent to persons having skill in the relevant art.

Data stored in the computer system 500 (e.g., in the main memory 508and/or the secondary memory 510) may be stored on any type of suitablecomputer readable media, such as optical storage (e.g., a compact disc,digital versatile disc, Blu-ray disc, etc.) or magnetic tape storage(e.g., a hard disk drive). The data may be configured in any type ofsuitable database configuration, such as a relational database, astructured query language (SQL) database, a distributed database, anobject database, etc. Suitable configurations and storage types will beapparent to persons having skill in the relevant art.

The computer system 500 may also include a communications interface 524.The communications interface 524 may be configured to allow software anddata to be transferred between the computer system 500 and externaldevices. Exemplary communications interfaces 524 may include a modem, anetwork interface (e.g., an Ethernet card), a communications port, aPCMCIA slot and card, etc. Software and data transferred via thecommunications interface 524 may be in the form of signals, which may beelectronic, electromagnetic, optical, or other signals as will beapparent to persons having skill in the relevant art. The signals maytravel via a communications path 526, which may be configured to carrythe signals and may be implemented using wire, cable, fiber optics, aphone line, a cellular phone link, a radio frequency link, etc.

The computer system 500 may further include a display interface 502. Thedisplay interface 502 may be configured to allow data to be transferredbetween the computer system 500 and external display 530. Exemplarydisplay interfaces 502 may include high-definition multimedia interface(HDMI), digital visual interface (DVI), video graphics array (VGA), etc.The display 530 may be any suitable type of display for displaying datatransmitted via the display interface 502 of the computer system 500,including a cathode ray tube (CRT) display, liquid crystal display(LCD), light-emitting diode (LED) display, capacitive touch display,thin-film transistor (TFT) display, etc.

Computer program medium and computer usable medium may refer tomemories, such as the main memory 508 and secondary memory 510, whichmay be memory semiconductors (e.g., DRAMs, etc.). These computer programproducts may be means for providing software to the computer system 500.Computer programs (e.g., computer control logic) may be stored in themain memory 508 and/or the secondary memory 510. Computer programs mayalso be received via the communications interface 524. Such computerprograms, when executed, may enable computer system 500 to implement thepresent methods as discussed herein. In particular, the computerprograms, when executed, may enable processor device 504 to implementthe methods illustrated by FIGS. 2 and 4, as discussed herein.Accordingly, such computer programs may represent controllers of thecomputer system 500. Where the present disclosure is implemented usingsoftware, the software may be stored in a computer program product andloaded into the computer system 500 using the removable storage drive514, interface 520, and hard disk drive 512, or communications interface524.

The processor device 504 may comprise one or more modules or enginesconfigured to perform the functions of the computer system 500. Each ofthe modules or engines may be implemented using hardware and, in someinstances, may also utilize software, such as corresponding to programcode and/or programs stored in the main memory 508 or secondary memory510. In such instances, program code may be compiled by the processordevice 504 (e.g., by a compiling module or engine) prior to execution bythe hardware of the computer system 500. For example, the program codemay be source code written in a programming language that is translatedinto a lower level language, such as assembly language or machine code,for execution by the processor device 504 and/or any additional hardwarecomponents of the computer system 500.

The process of compiling may include the use of lexical analysis,pre-processing, parsing, semantic analysis, syntax-directed translation,code generation, code optimization, and any other techniques that may besuitable for translation of program code into a lower level languagesuitable for controlling the computer system 500 to perform thefunctions disclosed herein. It will be apparent to persons having skillin the relevant art that such processes result in the computer system500 being a specially configured computer system 500 uniquely programmedto perform the functions discussed above.

Techniques consistent with the present disclosure provide, among otherfeatures, systems and methods for enabling and performing communicationbetween blockchains on heterogeneous blockchain networks. While variousexemplary embodiments of the disclosed system and method have beendescribed above it should be understood that they have been presentedfor purposes of example only, not limitations. It is not exhaustive anddoes not limit the disclosure to the precise form disclosed.Modifications and variations are possible in light of the aboveteachings or may be acquired from practicing of the disclosure, withoutdeparting from the breadth or scope.

What is claimed is:
 1. A system for enabling communication betweenblockchains on heterogeneous blockchain networks, the system comprising:a sending blockchain network comprised of a sending blockchain thatincludes a plurality of blocks, each block including a block header andone or more transaction values associated with an identification requesttransmitted by the sending blockchain; a directory service nodeconfigured to receive the identification request from the sendingblockchain, and identify a receiving blockchain, which forms part of areceiving blockchain network; and an identity service node configured toreceive a trust request from the directory service node to determinewhether a valid trust certificate is available for the receivingblockchain and enable communication between the sending blockchain andthe receiving blockchain, when the valid trust certificate is determinedto be available.
 2. The system of claim 1, wherein the directory servicenode is configured to identify the receiving blockchain by applying oneor more machine learning algorithms on the identification request. 3.The system of claim 1, wherein the directory service node is configuredto identify the receiving blockchain based on a preference of thesending blockchain.
 4. The system of claim 1, wherein the identificationrequest includes one or more of zip code information, pricinginformation, foreign exchange (fx) information, and unique identifierinformation of the receiving blockchain.
 5. The system of claim 1,wherein the identification request includes information regarding priorcommunication between the sending blockchain and the receivingblockchain.
 6. The system of claim 1, the enabled communication allowscontinuous data exchange between the sending blockchain and receivingblockchain without a re-verification of the valid trust certificate. 7.The system of claim 1, wherein the sending blockchain network includesmultiple blockchains.
 8. The system of claim 1, wherein the receivingblockchain network includes multiple blockchains.
 9. The system of claim1, wherein the directory service node forms a part of the sendingblockchain network or is external to the sending blockchain network. 10.The system of claim 1, wherein the identity service node forms a part ofthe sending blockchain network, is external to the sending blockchainnetwork.
 11. A method for enabling communication between blockchains onheterogeneous blockchain networks, the method comprising: transmittingan identification request from a sending blockchain to a directoryservice node, wherein the sending blockchain includes a plurality ofblocks, each block including a block header and one or more transactionvalues associated with the identification request, and the sendingblockchain forms a part of a sending blockchain network; identifying,via the directory service node, a receiving blockchain that forms partof a receiving blockchain network; and receiving, at an identity servicenode, a trust request from the directory service node to determinewhether a valid trust certificate is available for the receivingblockchain; and enabling communication between the sending blockchainand the receiving blockchain, when the valid trust certificate isdetermined to be available.
 12. The method of claim 1, wherein theidentifying the receiving blockchain includes applying one or moremachine learning algorithms on the identification request.
 13. Themethod of claim 1, wherein the identifying the receiving blockchain isbased on a preference of the sending blockchain.
 14. The method of claim11, wherein the identification request includes one or more of zip codeinformation, pricing information, foreign exchange (fx) information, andunique identifier information of the receiving blockchain.
 15. Themethod of claim 11, wherein the identification request includesinformation regarding prior communication between the sending blockchainand the receiving blockchain.
 16. The method of claim 11, the enablingcommunication includes continuous data exchange between the sendingblockchain and receiving blockchain without a re-verification of thevalid trust certificate.
 17. The method of claim 11, wherein the sendingblockchain network includes multiple blockchains.
 18. The method ofclaim 11, wherein the receiving blockchain network includes multipleblockchains.
 19. The method of claim 11, wherein the directory servicenode forms a part of the sending blockchain network or is external tothe sending blockchain network.
 20. The method of claim 11, wherein theidentity service node forms a part of the sending blockchain network oris external to the sending blockchain network.